Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4912fddc20ad3586b8ebbc22f1fcd3abc04aebe38a6a330c0275d0631fa6e6f9

Tx prefix hash: 4fcf63efefa53f903e7ea24ac68d7695c7f3988b7bb8f2a74af8a25cec81bb33
Tx public key: 33a9cf40eb91a72c03c4701034ab974d3e4625062c3c7d809b7930e228e14daf
Timestamp: 1729029098 Timestamp [UCT]: 2024-10-15 21:51:38 Age [y:d:h:m:s]: 00:099:15:21:30
Block: 1132418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71169 RingCT/type: yes/0
Extra: 0133a9cf40eb91a72c03c4701034ab974d3e4625062c3c7d809b7930e228e14daf021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d417c5db0a2ecba31409da5adbbe0101b0bcd97fb48aae2093ed0e2877051005 0.600000000000 1615333 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": 1132428, "vin": [ { "gen": { "height": 1132418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d417c5db0a2ecba31409da5adbbe0101b0bcd97fb48aae2093ed0e2877051005" } } ], "extra": [ 1, 51, 169, 207, 64, 235, 145, 167, 44, 3, 196, 112, 16, 52, 171, 151, 77, 62, 70, 37, 6, 44, 60, 125, 128, 155, 121, 48, 226, 40, 225, 77, 175, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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