Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99f4a54bc3b5b27f33ea890ce65bb817af4126916cabc3faf23efe9f4109c205

Tx prefix hash: cf427270aefa05c24b94da97d7b7e6e67fcebe045dbf94f4500a85746591e843
Tx public key: 299c1b0d5dcca358559fe42584958ad90357c7304d1f2e926ec6a7ad851433b2
Timestamp: 1701566595 Timestamp [UCT]: 2023-12-03 01:23:15 Age [y:d:h:m:s]: 01:162:17:17:01
Block: 904734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377481 RingCT/type: yes/0
Extra: 01299c1b0d5dcca358559fe42584958ad90357c7304d1f2e926ec6a7ad851433b202110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.616936779000 dcy

stealth address amount amount idx
00: 526068480a7e7173911cdc7094671eda56eeb1859547c292f13f331405b2e4f4 0.616936779000 1361507 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": 904744, "vin": [ { "gen": { "height": 904734 } } ], "vout": [ { "amount": 616936779, "target": { "key": "526068480a7e7173911cdc7094671eda56eeb1859547c292f13f331405b2e4f4" } } ], "extra": [ 1, 41, 156, 27, 13, 93, 204, 163, 88, 85, 159, 228, 37, 132, 149, 138, 217, 3, 87, 199, 48, 77, 31, 46, 146, 110, 198, 167, 173, 133, 20, 51, 178, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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