Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04f15e47caee5afeaf4b8893aae09ec2f61775f049fa6b91fb5d2def26bd7834

Tx prefix hash: d576770d35bad81311f844884cc038cf19cf29b5dfb25d55f40363989bc1c076
Tx public key: 677dbe3c22e85dd957756b562ad9a422b6fb96107912e5e326ca5dba387f453e
Timestamp: 1701012679 Timestamp [UCT]: 2023-11-26 15:31:19 Age [y:d:h:m:s]: 01:169:02:14:04
Block: 900133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382055 RingCT/type: yes/0
Extra: 01677dbe3c22e85dd957756b562ad9a422b6fb96107912e5e326ca5dba387f453e021100000002faf35c9c000000000000000000

1 output(s) for total of 0.638977684000 dcy

stealth address amount amount idx
00: ed77161a2ee0f979b9f039683fb8fc9fbc2e7e606298b23a460e2e896a4ed20b 0.638977684000 1356610 of 0

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": 900143, "vin": [ { "gen": { "height": 900133 } } ], "vout": [ { "amount": 638977684, "target": { "key": "ed77161a2ee0f979b9f039683fb8fc9fbc2e7e606298b23a460e2e896a4ed20b" } } ], "extra": [ 1, 103, 125, 190, 60, 34, 232, 93, 217, 87, 117, 107, 86, 42, 217, 164, 34, 182, 251, 150, 16, 121, 18, 229, 227, 38, 202, 93, 186, 56, 127, 69, 62, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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