Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd9671777c0e54e3d8b60305337367be6515cf53834c424e8c4a1980f9b4e721

Tx prefix hash: 630c44418992e3dbb57bfb68f64fb92c230822755f7ca3b45da1a4c4d8cab099
Tx public key: 3c9bf8f4c0c1da38471932a48bf538b7fea3ad4408a1d6b9b0315af63c363514
Timestamp: 1684436278 Timestamp [UCT]: 2023-05-18 18:57:58 Age [y:d:h:m:s]: 01:243:05:11:50
Block: 762966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435265 RingCT/type: yes/0
Extra: 013c9bf8f4c0c1da38471932a48bf538b7fea3ad4408a1d6b9b0315af63c363514021100000005faf35c9c000000000000000000

1 output(s) for total of 1.819684926000 dcy

stealth address amount amount idx
00: 0f34e0d51d1750766360559c5deb31bc84cc6893370332959f5eb758c2e0054d 1.819684926000 1211751 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": 762976, "vin": [ { "gen": { "height": 762966 } } ], "vout": [ { "amount": 1819684926, "target": { "key": "0f34e0d51d1750766360559c5deb31bc84cc6893370332959f5eb758c2e0054d" } } ], "extra": [ 1, 60, 155, 248, 244, 192, 193, 218, 56, 71, 25, 50, 164, 139, 245, 56, 183, 254, 163, 173, 68, 8, 161, 214, 185, 176, 49, 90, 246, 60, 54, 53, 20, 2, 17, 0, 0, 0, 5, 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