Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1937fcdab1f7ba67782a9f0470c3f600a48149c3355a857ab02cdc5988530968

Tx prefix hash: 677b6814fe7bff2e600a4d17f4b7549f79249affdeff0790ef2c959bbaea8a74
Tx public key: f149c6b612aa203a6fdc06a3181bfc254caf1e1956300de57ce27b527f7a0cd8
Timestamp: 1726244443 Timestamp [UCT]: 2024-09-13 16:20:43 Age [y:d:h:m:s]: 00:252:12:11:15
Block: 1109322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180341 RingCT/type: yes/0
Extra: 01f149c6b612aa203a6fdc06a3181bfc254caf1e1956300de57ce27b527f7a0cd802110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 112f967f319108df5254997136c3d936a2d53c736ccd806c0d7cab6d6014b823 0.600000000000 1587531 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": 1109332, "vin": [ { "gen": { "height": 1109322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "112f967f319108df5254997136c3d936a2d53c736ccd806c0d7cab6d6014b823" } } ], "extra": [ 1, 241, 73, 198, 182, 18, 170, 32, 58, 111, 220, 6, 163, 24, 27, 252, 37, 76, 175, 30, 25, 86, 48, 13, 229, 124, 226, 123, 82, 127, 122, 12, 216, 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