Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f5e15c50c5e673587f717faad2006234a8bb445cc1058432fcb387a9b5c4213

Tx prefix hash: a9c0d30726eb89e6a8bebe46d9aed4d1bcf430bbeee0f66029fe8b0b15202837
Tx public key: 96ca3b71fd0330c1dca5b705d1738bcda1f76f3d4ae5bc85afb874c93d646244
Timestamp: 1729138041 Timestamp [UCT]: 2024-10-17 04:07:21 Age [y:d:h:m:s]: 00:148:14:57:28
Block: 1133316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106004 RingCT/type: yes/0
Extra: 0196ca3b71fd0330c1dca5b705d1738bcda1f76f3d4ae5bc85afb874c93d64624402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cf99de1859115f7f6bee2546da4bcfebe5670140ea56784d0f3cc00e5f0428b 0.600000000000 1616413 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": 1133326, "vin": [ { "gen": { "height": 1133316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cf99de1859115f7f6bee2546da4bcfebe5670140ea56784d0f3cc00e5f0428b" } } ], "extra": [ 1, 150, 202, 59, 113, 253, 3, 48, 193, 220, 165, 183, 5, 209, 115, 139, 205, 161, 247, 111, 61, 74, 229, 188, 133, 175, 184, 116, 201, 61, 100, 98, 68, 2, 17, 0, 0, 0, 1, 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