Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1df22bd80eaad54258f198aa0a1c9a718659e0ed3eeabc68fb773398a6cd3fcc

Tx prefix hash: f3fb9c4e21d5431c540378786019d3425c21a2f6bb7a774c589a44d1804ecd67
Tx public key: 7532fdc4fd3eedfc85c0862596757d3454555d3325f0cba913da68b048d02053
Timestamp: 1709496471 Timestamp [UCT]: 2024-03-03 20:07:51 Age [y:d:h:m:s]: 01:249:16:21:02
Block: 970484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437156 RingCT/type: yes/0
Extra: 017532fdc4fd3eedfc85c0862596757d3454555d3325f0cba913da68b048d0205302110000000249a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 955f68d24fc6f3b4619a87d10ce963d1dd87064fb13c3fe3da59f8f7feb18654 0.600000000000 1430339 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": 970494, "vin": [ { "gen": { "height": 970484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "955f68d24fc6f3b4619a87d10ce963d1dd87064fb13c3fe3da59f8f7feb18654" } } ], "extra": [ 1, 117, 50, 253, 196, 253, 62, 237, 252, 133, 192, 134, 37, 150, 117, 125, 52, 84, 85, 93, 51, 37, 240, 203, 169, 19, 218, 104, 176, 72, 208, 32, 83, 2, 17, 0, 0, 0, 2, 73, 161, 133, 187, 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