Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f3ee95976d22b4cbf9e9886f5a4b2648763c5c4270bd9e4226b3841347ac663

Tx prefix hash: 49eb6e3c60490435be1abd4b8396fcfb9bbe1f0ecfa5df9126e318ac60db0a62
Tx public key: bffec48ae98d1ab541eb2af82543f5607d4f30e3229d61d0213e730ba4a191de
Timestamp: 1717123383 Timestamp [UCT]: 2024-05-31 02:43:03 Age [y:d:h:m:s]: 00:177:20:26:51
Block: 1033706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127296 RingCT/type: yes/0
Extra: 01bffec48ae98d1ab541eb2af82543f5607d4f30e3229d61d0213e730ba4a191de02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7515edad588d857ec2cdbb04079cea2d8a7c6ee3b64a03cbdd0966ba49ee5e0b 0.600000000000 1502177 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": 1033716, "vin": [ { "gen": { "height": 1033706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7515edad588d857ec2cdbb04079cea2d8a7c6ee3b64a03cbdd0966ba49ee5e0b" } } ], "extra": [ 1, 191, 254, 196, 138, 233, 141, 26, 181, 65, 235, 42, 248, 37, 67, 245, 96, 125, 79, 48, 227, 34, 157, 97, 208, 33, 62, 115, 11, 164, 161, 145, 222, 2, 17, 0, 0, 0, 1, 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