Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a97f86779bf61dcdcb62d2b7b0e0e3b8736c88d9683e873a0d266d06610848a1

Tx prefix hash: 0fe70d06ba7542ee89678f4cc17dcd18642e4e8e5711abb3f05f3b2730d8a971
Tx public key: 74c52c3530ea25e599e43e287f7f25a7f63d5c2b329313fd50bbc1aee4a85ec5
Timestamp: 1721927638 Timestamp [UCT]: 2024-07-25 17:13:58 Age [y:d:h:m:s]: 00:254:10:33:40
Block: 1073534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181758 RingCT/type: yes/0
Extra: 0174c52c3530ea25e599e43e287f7f25a7f63d5c2b329313fd50bbc1aee4a85ec502110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af0f9885ac5f37990a3ba41c16ed325e4e7096ef7339f2019841bcf18475bb7d 0.600000000000 1546037 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": 1073544, "vin": [ { "gen": { "height": 1073534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af0f9885ac5f37990a3ba41c16ed325e4e7096ef7339f2019841bcf18475bb7d" } } ], "extra": [ 1, 116, 197, 44, 53, 48, 234, 37, 229, 153, 228, 62, 40, 127, 127, 37, 167, 246, 61, 92, 43, 50, 147, 19, 253, 80, 187, 193, 174, 228, 168, 94, 197, 2, 17, 0, 0, 0, 15, 233, 20, 221, 21, 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