Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0865efabb7141b3909384d043010424db1b833d6fbba84a289b8f77aae22af6

Tx prefix hash: 7e57b4417492ec11560f2fdb99b44180a8237a07b13f422d98857a8bd1f59f7a
Tx public key: f4576b88a1a1ff28acee02a67a330094fd8d409f5e057211dc6c76bfab994db6
Timestamp: 1735338815 Timestamp [UCT]: 2024-12-27 22:33:35 Age [y:d:h:m:s]: 00:085:02:51:31
Block: 1184582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60634 RingCT/type: yes/0
Extra: 01f4576b88a1a1ff28acee02a67a330094fd8d409f5e057211dc6c76bfab994db60211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a074b09d1f49ee19b0bdafc2c76860789ed70f74592748f41568f2f3dcdfddc7 0.600000000000 1671041 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": 1184592, "vin": [ { "gen": { "height": 1184582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a074b09d1f49ee19b0bdafc2c76860789ed70f74592748f41568f2f3dcdfddc7" } } ], "extra": [ 1, 244, 87, 107, 136, 161, 161, 255, 40, 172, 238, 2, 166, 122, 51, 0, 148, 253, 141, 64, 159, 94, 5, 114, 17, 220, 108, 118, 191, 171, 153, 77, 182, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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