Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3716cdc367ea7f7af7adcbc951039b4c8894ab248449a2b778d48322de2f101b

Tx prefix hash: d7be37e7c9381817aa9dfb2d2b9b678b5affc16fcf362ee248bed9627ca6c704
Tx public key: fe6c10ed69350ea8007dbf68f7dd36c52ae9fea50e0f6fccde9cb4e99f185a51
Timestamp: 1737724669 Timestamp [UCT]: 2025-01-24 13:17:49 Age [y:d:h:m:s]: 00:144:09:47:09
Block: 1204309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102937 RingCT/type: yes/0
Extra: 01fe6c10ed69350ea8007dbf68f7dd36c52ae9fea50e0f6fccde9cb4e99f185a510211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7267fec95313f2601ffc621692df998f4ebcf93478df40e761d02fe4ad648f6 0.600000000000 1690994 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": 1204319, "vin": [ { "gen": { "height": 1204309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7267fec95313f2601ffc621692df998f4ebcf93478df40e761d02fe4ad648f6" } } ], "extra": [ 1, 254, 108, 16, 237, 105, 53, 14, 168, 0, 125, 191, 104, 247, 221, 54, 197, 42, 233, 254, 165, 14, 15, 111, 204, 222, 156, 180, 233, 159, 24, 90, 81, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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