Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 689a07aaa2848b1c6a8ce006b2e4e92db132fb3660504658cac2e07c498d6570

Tx prefix hash: f7f17c793e5e4113a0497aa033b27c1c1a4754e70d6ed91cc919cf74983c1fe7
Tx public key: 825ac6127a99137df8fe702a5a1562c4ac72c365a94f463dbcde6933d6c0f8c7
Timestamp: 1702283474 Timestamp [UCT]: 2023-12-11 08:31:14 Age [y:d:h:m:s]: 01:335:13:03:08
Block: 910677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498674 RingCT/type: yes/0
Extra: 01825ac6127a99137df8fe702a5a1562c4ac72c365a94f463dbcde6933d6c0f8c702110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c8ddcb7201b62948611df89adfe6c0d0ea3e937c9141b79599de45718be7049 0.600000000000 1367842 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": 910687, "vin": [ { "gen": { "height": 910677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c8ddcb7201b62948611df89adfe6c0d0ea3e937c9141b79599de45718be7049" } } ], "extra": [ 1, 130, 90, 198, 18, 122, 153, 19, 125, 248, 254, 112, 42, 90, 21, 98, 196, 172, 114, 195, 101, 169, 79, 70, 61, 188, 222, 105, 51, 214, 192, 248, 199, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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