Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b1bf0a94a7446df0eb4c1640776af9bcb854ede683e834dcccb844bbb469c1f

Tx prefix hash: 8d906a0571f3cb8d1ac1e072bc2368a1011118a999ec5567e01c09a8a972aea2
Tx public key: 1f7e8c898bbafec63fc417f1ba6bcfb3881d608d23958ad9e21d2e3ced274189
Timestamp: 1732803057 Timestamp [UCT]: 2024-11-28 14:10:57 Age [y:d:h:m:s]: 00:126:14:14:11
Block: 1163605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90276 RingCT/type: yes/0
Extra: 011f7e8c898bbafec63fc417f1ba6bcfb3881d608d23958ad9e21d2e3ced2741890211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c098116362cb2f72cfb4bd5e93770a277ae5abda4ecb5b60e16d33881bd26b84 0.600000000000 1649272 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": 1163615, "vin": [ { "gen": { "height": 1163605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c098116362cb2f72cfb4bd5e93770a277ae5abda4ecb5b60e16d33881bd26b84" } } ], "extra": [ 1, 31, 126, 140, 137, 139, 186, 254, 198, 63, 196, 23, 241, 186, 107, 207, 179, 136, 29, 96, 141, 35, 149, 138, 217, 226, 29, 46, 60, 237, 39, 65, 137, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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