Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89d8e7a951818d85d1d68f637d5ac5ab5b4ac1487b59464626b1f3321872680d

Tx prefix hash: dd62cb67b51a40b95a54c887c90b3646a176c04c8ca10e0669d7040199c68aee
Tx public key: fa4e97d4f5d86da61acd79a7badbccd3ddfb4bc41eb25acd7c22b080ec20c7c4
Timestamp: 1728888455 Timestamp [UCT]: 2024-10-14 06:47:35 Age [y:d:h:m:s]: 00:087:21:01:10
Block: 1131250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62798 RingCT/type: yes/0
Extra: 01fa4e97d4f5d86da61acd79a7badbccd3ddfb4bc41eb25acd7c22b080ec20c7c402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 170975f6cf3a4273621a63a1c4eacb362f78aeefce105118bfdf55a0bc20bfb5 0.600000000000 1614131 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": 1131260, "vin": [ { "gen": { "height": 1131250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "170975f6cf3a4273621a63a1c4eacb362f78aeefce105118bfdf55a0bc20bfb5" } } ], "extra": [ 1, 250, 78, 151, 212, 245, 216, 109, 166, 26, 205, 121, 167, 186, 219, 204, 211, 221, 251, 75, 196, 30, 178, 90, 205, 124, 34, 176, 128, 236, 32, 199, 196, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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