Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e11e98ee2b5a245b9ff5d1f7658d1e8081cfc16a495e925216cef26dc74d2104

Tx prefix hash: 608cf62d4cef17787a35c10dc0ce535582ae47ca3f0cd15801081a4217b93000
Tx public key: d45cf76b5ca863825b82bc7f2a2631752c1fbdf6e9c5ba0b27bdb014b7d15ba0
Timestamp: 1718501841 Timestamp [UCT]: 2024-06-16 01:37:21 Age [y:d:h:m:s]: 00:132:09:44:10
Block: 1045154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94791 RingCT/type: yes/0
Extra: 01d45cf76b5ca863825b82bc7f2a2631752c1fbdf6e9c5ba0b27bdb014b7d15ba00211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74bdb7be6e3ea1a93c331cbc8c1286c4c1e2b266f923b8b00d95c99b60188e30 0.600000000000 1514651 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": 1045164, "vin": [ { "gen": { "height": 1045154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74bdb7be6e3ea1a93c331cbc8c1286c4c1e2b266f923b8b00d95c99b60188e30" } } ], "extra": [ 1, 212, 92, 247, 107, 92, 168, 99, 130, 91, 130, 188, 127, 42, 38, 49, 117, 44, 31, 189, 246, 233, 197, 186, 11, 39, 189, 176, 20, 183, 209, 91, 160, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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