Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5064d671e9b7a157e8989aafafb7b8d2b1d1643afa649f6d2be392964559dc2f

Tx prefix hash: 4356e8b0789597bb44bf086c2557908456e898ad228d65f02d3800bbce68467c
Tx public key: fb52c0adffc5c3f2a6e64c1f66b9d20daf8198415a1a7c907a02a93e40339be9
Timestamp: 1744709551 Timestamp [UCT]: 2025-04-15 09:32:31 Age [y:d:h:m:s]: 00:252:18:20:38
Block: 1261907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178408 RingCT/type: yes/0
Extra: 01fb52c0adffc5c3f2a6e64c1f66b9d20daf8198415a1a7c907a02a93e40339be90211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e34b452b15344eb7c572bd60375ff015e29eaee984681f6306f47f3001259cc 0.600000000000 1749082 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": 1261917, "vin": [ { "gen": { "height": 1261907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e34b452b15344eb7c572bd60375ff015e29eaee984681f6306f47f3001259cc" } } ], "extra": [ 1, 251, 82, 192, 173, 255, 197, 195, 242, 166, 230, 76, 31, 102, 185, 210, 13, 175, 129, 152, 65, 90, 26, 124, 144, 122, 2, 169, 62, 64, 51, 155, 233, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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