Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9117022077326f69f11311f74d7a4561f226e003105a61cb88dabc333b856042

Tx prefix hash: 08e3dbcd3afc3d17170e606176e989417e0910fb3c3a157d5f049268df9d4254
Tx public key: eac2b024b5eb68d379c633797429dca2d2a246ac9e63683112153218aa5cfe5f
Timestamp: 1726824313 Timestamp [UCT]: 2024-09-20 09:25:13 Age [y:d:h:m:s]: 00:199:19:30:51
Block: 1114128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142619 RingCT/type: yes/0
Extra: 01eac2b024b5eb68d379c633797429dca2d2a246ac9e63683112153218aa5cfe5f021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfdd71ccb1c9f3773b863dc52dc9be1c0345f7f483878f6e9bcd2a6369f12409 0.600000000000 1593927 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": 1114138, "vin": [ { "gen": { "height": 1114128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfdd71ccb1c9f3773b863dc52dc9be1c0345f7f483878f6e9bcd2a6369f12409" } } ], "extra": [ 1, 234, 194, 176, 36, 181, 235, 104, 211, 121, 198, 51, 121, 116, 41, 220, 162, 210, 162, 70, 172, 158, 99, 104, 49, 18, 21, 50, 24, 170, 92, 254, 95, 2, 17, 0, 0, 0, 5, 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