Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 736a999ea17a0e8bfd460b13b9cdd3b9f9516f29b08725c6d354e8eb9603b061

Tx prefix hash: 91419f7091741ffe81a1b11830e9a7316f4163be9b7996d93273898687b4bfcf
Tx public key: 342a2ca77d8874c6a32bc3f1256c285d06f0d7d12936ea4017ecaff652d4041b
Timestamp: 1735381047 Timestamp [UCT]: 2024-12-28 10:17:27 Age [y:d:h:m:s]: 00:328:07:26:31
Block: 1184946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232154 RingCT/type: yes/0
Extra: 01342a2ca77d8874c6a32bc3f1256c285d06f0d7d12936ea4017ecaff652d4041b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2273d4fb4c5adf6733e6173eb0a832d05c0809d29a814647367b079cb220ec5 0.600000000000 1671409 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": 1184956, "vin": [ { "gen": { "height": 1184946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2273d4fb4c5adf6733e6173eb0a832d05c0809d29a814647367b079cb220ec5" } } ], "extra": [ 1, 52, 42, 44, 167, 125, 136, 116, 198, 163, 43, 195, 241, 37, 108, 40, 93, 6, 240, 215, 209, 41, 54, 234, 64, 23, 236, 175, 246, 82, 212, 4, 27, 2, 17, 0, 0, 0, 1, 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