Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35df9772b7f84b4e09bc352bd9a7f0dca1eb691fc117bfe1573d1a0580c4f50c

Tx prefix hash: 98d055ab2fec24e22a24cdcf978d66c4dda0fb840a70d17d27c77e0ee76edb48
Tx public key: 6d5490a5b689a2b8127aaf91c78301614af56076a95d80147506e45d11539c1f
Timestamp: 1718583836 Timestamp [UCT]: 2024-06-17 00:23:56 Age [y:d:h:m:s]: 00:221:22:48:20
Block: 1045829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158766 RingCT/type: yes/0
Extra: 016d5490a5b689a2b8127aaf91c78301614af56076a95d80147506e45d11539c1f02110000000e52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a3cd3668a0b155234fe8a0e1d1ba26b26568b48851d2aa7ee9e6e709a64b51e 0.600000000000 1515516 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": 1045839, "vin": [ { "gen": { "height": 1045829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a3cd3668a0b155234fe8a0e1d1ba26b26568b48851d2aa7ee9e6e709a64b51e" } } ], "extra": [ 1, 109, 84, 144, 165, 182, 137, 162, 184, 18, 122, 175, 145, 199, 131, 1, 97, 74, 245, 96, 118, 169, 93, 128, 20, 117, 6, 228, 93, 17, 83, 156, 31, 2, 17, 0, 0, 0, 14, 82, 212, 126, 148, 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