Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86d2f79865bb4af9785969cf41e640b7eff71b6f3a9e997c72051ac490f466b6

Tx prefix hash: 9ac34621f0031f8813c1946db31bcf2317ec6953746f3d0d99a2f8ec0b1cd5e1
Tx public key: 3e0a25e4390087f6c3c64fd4e8860c77ac97cc1a3949d26e9e15f4143a3eb145
Timestamp: 1718619784 Timestamp [UCT]: 2024-06-17 10:23:04 Age [y:d:h:m:s]: 00:363:02:35:49
Block: 1046114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259428 RingCT/type: yes/0
Extra: 013e0a25e4390087f6c3c64fd4e8860c77ac97cc1a3949d26e9e15f4143a3eb14502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da4ae43bcaa09bf10281f5e0824aae024a54b72e274bdb340357fc8f4378878f 0.600000000000 1515881 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": 1046124, "vin": [ { "gen": { "height": 1046114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da4ae43bcaa09bf10281f5e0824aae024a54b72e274bdb340357fc8f4378878f" } } ], "extra": [ 1, 62, 10, 37, 228, 57, 0, 135, 246, 195, 198, 79, 212, 232, 134, 12, 119, 172, 151, 204, 26, 57, 73, 210, 110, 158, 21, 244, 20, 58, 62, 177, 69, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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