Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 736632dd057ab3f9594ff3bc181e120ff97c5a8f49fafd7977f0bd750c09764c

Tx prefix hash: 9562455cc20a53d4979a230cd1a6c26ad5a9d4c4c44ca06ebd7a1d1d65378c12
Tx public key: fe6f2b0a841ff458a4be732c353cce167395d0ba5f66a4fed2497e2084dd1056
Timestamp: 1730492948 Timestamp [UCT]: 2024-11-01 20:29:08 Age [y:d:h:m:s]: 00:081:19:25:39
Block: 1144461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58488 RingCT/type: yes/0
Extra: 01fe6f2b0a841ff458a4be732c353cce167395d0ba5f66a4fed2497e2084dd1056021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b06c842c392848d4a0ab081e4c5a7b9a0131ef42c7991813ed1788aea4f0384d 0.600000000000 1628684 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": 1144471, "vin": [ { "gen": { "height": 1144461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b06c842c392848d4a0ab081e4c5a7b9a0131ef42c7991813ed1788aea4f0384d" } } ], "extra": [ 1, 254, 111, 43, 10, 132, 31, 244, 88, 164, 190, 115, 44, 53, 60, 206, 22, 115, 149, 208, 186, 95, 102, 164, 254, 210, 73, 126, 32, 132, 221, 16, 86, 2, 17, 0, 0, 0, 5, 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