Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db6b23e0e9ffc8207a527b32f487458cc8b40523fac8f276b4fe65d5f1de3756

Tx prefix hash: 6fbfc912143194867b3dfadada9e262108a58c691c55dcf441b022d6c461be98
Tx public key: 75535d6ef8d0656f2771638aa94c8df6fe6caa55916dc9e582e61c974ad9428f
Timestamp: 1728702009 Timestamp [UCT]: 2024-10-12 03:00:09 Age [y:d:h:m:s]: 00:165:09:25:48
Block: 1129716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117956 RingCT/type: yes/0
Extra: 0175535d6ef8d0656f2771638aa94c8df6fe6caa55916dc9e582e61c974ad9428f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccd9b03cceb17a8788ab9f3afa39cc8d5ad9a358a14ac2332925f857c71f3301 0.600000000000 1612561 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": 1129726, "vin": [ { "gen": { "height": 1129716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccd9b03cceb17a8788ab9f3afa39cc8d5ad9a358a14ac2332925f857c71f3301" } } ], "extra": [ 1, 117, 83, 93, 110, 248, 208, 101, 111, 39, 113, 99, 138, 169, 76, 141, 246, 254, 108, 170, 85, 145, 109, 201, 229, 130, 230, 28, 151, 74, 217, 66, 143, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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