Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0f5dad6eef664ed52c796806e7a853a53df42042c9c31c244aba0ba6980d52b3

Tx prefix hash: cf94f129306629e0f2f8e55df635bcbef6ddda7ee8dca8cdb5608e2badba8947
Tx public key: 84b20413315ba83efe7bb96ddbbfb8d63a8e4b3196fc09d5aa0379e8d41755c4
Timestamp: 1715605030 Timestamp [UCT]: 2024-05-13 12:57:10 Age [y:d:h:m:s]: 00:181:15:41:15
Block: 1021141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130000 RingCT/type: yes/0
Extra: 0184b20413315ba83efe7bb96ddbbfb8d63a8e4b3196fc09d5aa0379e8d41755c4021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f3fd580fbc5c87c38cd0c0291eb94a21467c4758586217d4be9180291e7ee33 0.600000000000 1485364 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1021151, "vin": [ { "gen": { "height": 1021141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f3fd580fbc5c87c38cd0c0291eb94a21467c4758586217d4be9180291e7ee33" } } ], "extra": [ 1, 132, 178, 4, 19, 49, 91, 168, 62, 254, 123, 185, 109, 219, 191, 184, 214, 58, 142, 75, 49, 150, 252, 9, 213, 170, 3, 121, 232, 212, 23, 85, 196, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8