Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f056043fd41e1e0276b3bbe2aaacdab1baa1e5dd79e2c13f95a6d017ba275241

Tx prefix hash: b19375fae6b78adf9e989d47eb3c58fef1ed65eed2b76c31f86db1ad079a71c6
Tx public key: 28f6cfd9c88253661af0490fbc8c577a8d6da05af2314b067f1596c4b851904c
Timestamp: 1745848921 Timestamp [UCT]: 2025-04-28 14:02:01 Age [y:d:h:m:s]: 00:205:16:50:38
Block: 1271347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144719 RingCT/type: yes/0
Extra: 0128f6cfd9c88253661af0490fbc8c577a8d6da05af2314b067f1596c4b851904c0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf8bad9b6b3464bbd9725b9fed487c5054147d01b3bd748fa73050d66b524a61 0.600000000000 1758608 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": 1271357, "vin": [ { "gen": { "height": 1271347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf8bad9b6b3464bbd9725b9fed487c5054147d01b3bd748fa73050d66b524a61" } } ], "extra": [ 1, 40, 246, 207, 217, 200, 130, 83, 102, 26, 240, 73, 15, 188, 140, 87, 122, 141, 109, 160, 90, 242, 49, 75, 6, 127, 21, 150, 196, 184, 81, 144, 76, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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