Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 731f810b80b79b225258a1a801bfb208a8c222e1c0df9ab3bfe3a1d63dc7ecd1

Tx prefix hash: b9e91f91bed166a08ac2e64e01ecec7fe529f9374ff0eff1f634100f9e9b91e7
Tx public key: 639f6d56afed64cd80e574223c0daec98e98e5752d6d1a5d7ca56c439ab86748
Timestamp: 1749281224 Timestamp [UCT]: 2025-06-07 07:27:04 Age [y:d:h:m:s]: 00:164:10:25:04
Block: 1299765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115209 RingCT/type: yes/0
Extra: 01639f6d56afed64cd80e574223c0daec98e98e5752d6d1a5d7ca56c439ab8674802110000000c43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a64072fce8ce2ce39ceb4e5507115f7772642878876487f748e35cb41ee60c6a 0.600000000000 1787304 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": 1299775, "vin": [ { "gen": { "height": 1299765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a64072fce8ce2ce39ceb4e5507115f7772642878876487f748e35cb41ee60c6a" } } ], "extra": [ 1, 99, 159, 109, 86, 175, 237, 100, 205, 128, 229, 116, 34, 60, 13, 174, 201, 142, 152, 229, 117, 45, 109, 26, 93, 124, 165, 108, 67, 154, 184, 103, 72, 2, 17, 0, 0, 0, 12, 67, 132, 109, 102, 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