Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7116560267c8d5e77083b847590fa69f92ce5a2e55e016dd49be51eb3280be4d

Tx prefix hash: 5b405f1adb265bcbab4ba68f10ecc0793eb2ba575214a2681106762fe3a620bf
Tx public key: 313da531e7d27671a8b283f61e0a9a2ec8126589f17e137584d68665fd013c70
Timestamp: 1735170714 Timestamp [UCT]: 2024-12-25 23:51:54 Age [y:d:h:m:s]: 00:090:02:07:20
Block: 1183209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64157 RingCT/type: yes/0
Extra: 01313da531e7d27671a8b283f61e0a9a2ec8126589f17e137584d68665fd013c70021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdef4ad67bca31e5d5131b87a5b2a1a1d7a1f2d08e46cb4a68329cadbe971477 0.600000000000 1669650 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": 1183219, "vin": [ { "gen": { "height": 1183209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdef4ad67bca31e5d5131b87a5b2a1a1d7a1f2d08e46cb4a68329cadbe971477" } } ], "extra": [ 1, 49, 61, 165, 49, 231, 210, 118, 113, 168, 178, 131, 246, 30, 10, 154, 46, 200, 18, 101, 137, 241, 126, 19, 117, 132, 214, 134, 101, 253, 1, 60, 112, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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