Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6403cd45017699f1c2c0385c2ffe4dbbf6c3dbbbee4ad69395344d428d16ec1d

Tx prefix hash: 6e9dd97b329f3b0aafed83d72090d8da0d9ead7c9f66016f662e542ff6ca6670
Tx public key: dc605335336cd8e5d3d62abe80df3a5ec6d558d85c6a2dbbca36938877f246e2
Timestamp: 1725634790 Timestamp [UCT]: 2024-09-06 14:59:50 Age [y:d:h:m:s]: 00:124:14:59:14
Block: 1104277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89126 RingCT/type: yes/0
Extra: 01dc605335336cd8e5d3d62abe80df3a5ec6d558d85c6a2dbbca36938877f246e202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5f1c7284d7b847c06fd8b711f966c39b99f9ede10cc78b38e16783d46f29ba9 0.600000000000 1581358 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": 1104287, "vin": [ { "gen": { "height": 1104277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5f1c7284d7b847c06fd8b711f966c39b99f9ede10cc78b38e16783d46f29ba9" } } ], "extra": [ 1, 220, 96, 83, 53, 51, 108, 216, 229, 211, 214, 42, 190, 128, 223, 58, 94, 198, 213, 88, 216, 92, 106, 45, 187, 202, 54, 147, 136, 119, 242, 70, 226, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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