Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8aa2fed86202cfcff504cc38e1bd8570ac5fe9adccdf01e27373027cf77b25b0

Tx prefix hash: 23ae0d0f0c7eb364ba811836ad5c20127fb4f147cc4acc7bf306f218384a7706
Tx public key: 02e272ac5c5a25ed37f9cf851bbb3e7930a0010929d734f455332cac1bed4d9e
Timestamp: 1703794512 Timestamp [UCT]: 2023-12-28 20:15:12 Age [y:d:h:m:s]: 02:031:22:48:50
Block: 923200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542461 RingCT/type: yes/0
Extra: 0102e272ac5c5a25ed37f9cf851bbb3e7930a0010929d734f455332cac1bed4d9e0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd445748244ba01d0eca5064f6a78a341389e897df36504d166b6fee89d1a39d 0.600000000000 1380926 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": 923210, "vin": [ { "gen": { "height": 923200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd445748244ba01d0eca5064f6a78a341389e897df36504d166b6fee89d1a39d" } } ], "extra": [ 1, 2, 226, 114, 172, 92, 90, 37, 237, 55, 249, 207, 133, 27, 187, 62, 121, 48, 160, 1, 9, 41, 215, 52, 244, 85, 51, 44, 172, 27, 237, 77, 158, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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