Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0c987c5e6a038476d7ad17e354acf948cbf67346a06379c225557caf23ea6ca

Tx prefix hash: 892f3ad272c22294aefa131186d4b2b8094de3fcdf829789c52582f8ba952280
Tx public key: 54d159bc46ab3ab5748b267366df451c26d7a6244529f6a4eb764455343b14a5
Timestamp: 1700740087 Timestamp [UCT]: 2023-11-23 11:48:07 Age [y:d:h:m:s]: 01:138:08:44:12
Block: 897883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360050 RingCT/type: yes/0
Extra: 0154d159bc46ab3ab5748b267366df451c26d7a6244529f6a4eb764455343b14a502110000000775e3f0e9000000000000000000

1 output(s) for total of 0.650041193000 dcy

stealth address amount amount idx
00: e0e0c178aeb3b0e23ca4f59dfc60309f477050d22565553a364b4555e060264d 0.650041193000 1354280 of 0

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": 897893, "vin": [ { "gen": { "height": 897883 } } ], "vout": [ { "amount": 650041193, "target": { "key": "e0e0c178aeb3b0e23ca4f59dfc60309f477050d22565553a364b4555e060264d" } } ], "extra": [ 1, 84, 209, 89, 188, 70, 171, 58, 181, 116, 139, 38, 115, 102, 223, 69, 28, 38, 215, 166, 36, 69, 41, 246, 164, 235, 118, 68, 85, 52, 59, 20, 165, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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