Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53865db5bcf70e8d390d0f8b5c56eb51c91c70c46c534bcceb0398ae631dcd28

Tx prefix hash: a171def88df68c6a80c9d78192a65f5c620c8284aa56134c3e7226b7b5fc8229
Tx public key: dcdfa96904838b7778028e927e45ab76c392c65473cbfa3a9814df179509b729
Timestamp: 1704553564 Timestamp [UCT]: 2024-01-06 15:06:04 Age [y:d:h:m:s]: 01:048:11:08:53
Block: 929484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295708 RingCT/type: yes/0
Extra: 01dcdfa96904838b7778028e927e45ab76c392c65473cbfa3a9814df179509b7290211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf9dc2f8e754dbf1caf6bad192058dd59d7911abdb4f6b11f893b980869dfdc0 0.600000000000 1387360 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": 929494, "vin": [ { "gen": { "height": 929484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf9dc2f8e754dbf1caf6bad192058dd59d7911abdb4f6b11f893b980869dfdc0" } } ], "extra": [ 1, 220, 223, 169, 105, 4, 131, 139, 119, 120, 2, 142, 146, 126, 69, 171, 118, 195, 146, 198, 84, 115, 203, 250, 58, 152, 20, 223, 23, 149, 9, 183, 41, 2, 17, 0, 0, 0, 3, 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