Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6648f31a6eb816addddd1755437df378fe6aac118199caa5f8b7dae4586420a

Tx prefix hash: 8da2760571d6f61d9b0667f38092ea7512994180fd84ad6b12bc2689874b6265
Tx public key: 607d9d07b070a6675c4e10da9f768035d4de027c65d88c3953b972c88ac17f6a
Timestamp: 1677690610 Timestamp [UCT]: 2023-03-01 17:10:10 Age [y:d:h:m:s]: 02:049:00:33:11
Block: 707670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556629 RingCT/type: yes/0
Extra: 01607d9d07b070a6675c4e10da9f768035d4de027c65d88c3953b972c88ac17f6a0211000000025029cbac000000000000000000

1 output(s) for total of 2.774568327000 dcy

stealth address amount amount idx
00: fdf0a25265304bb83ee0a9b3754ef55a120b4d292756a3f51f1e4e846634f2b9 2.774568327000 1151489 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": 707680, "vin": [ { "gen": { "height": 707670 } } ], "vout": [ { "amount": 2774568327, "target": { "key": "fdf0a25265304bb83ee0a9b3754ef55a120b4d292756a3f51f1e4e846634f2b9" } } ], "extra": [ 1, 96, 125, 157, 7, 176, 112, 166, 103, 92, 78, 16, 218, 159, 118, 128, 53, 212, 222, 2, 124, 101, 216, 140, 57, 83, 185, 114, 200, 138, 193, 127, 106, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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