Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d61bed76cdb5af8f4dd9c13c72f82c75bf88a368228e559a1c9c077a1ac0922d

Tx prefix hash: e274782c633a38529d8610e6b6ba8a7b7c9e2af627f1c8646f120d559857e7b5
Tx public key: 3184437c9d114dc7fef6c24d2537013e7c947f05a7f29a6225e9ba660f62bde0
Timestamp: 1702022599 Timestamp [UCT]: 2023-12-08 08:03:19 Age [y:d:h:m:s]: 01:044:17:23:46
Block: 908517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293291 RingCT/type: yes/0
Extra: 013184437c9d114dc7fef6c24d2537013e7c947f05a7f29a6225e9ba660f62bde002110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64a8ef152b34b1534b1030e7af131400c77e97803b2928248cecff5ed9921ee8 0.600000000000 1365550 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": 908527, "vin": [ { "gen": { "height": 908517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64a8ef152b34b1534b1030e7af131400c77e97803b2928248cecff5ed9921ee8" } } ], "extra": [ 1, 49, 132, 67, 124, 157, 17, 77, 199, 254, 246, 194, 77, 37, 55, 1, 62, 124, 148, 127, 5, 167, 242, 154, 98, 37, 233, 186, 102, 15, 98, 189, 224, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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