Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0730412f6a53957a65db5d46a3d4759df44ab7265de5aa23c4b65a7b0dd1f754

Tx prefix hash: d05125bc87d9359cb17b274e18efe52c3b2983fa622400901ef3627e942ccd40
Tx public key: b0e96119425a86080a51d3f1255d91ddcc777ca1f83a293010c1ee55979236cb
Timestamp: 1701660040 Timestamp [UCT]: 2023-12-04 03:20:40 Age [y:d:h:m:s]: 01:153:04:35:03
Block: 905500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370660 RingCT/type: yes/0
Extra: 01b0e96119425a86080a51d3f1255d91ddcc777ca1f83a293010c1ee55979236cb0211000000014b8f5122000000000000000000

1 output(s) for total of 0.613341830000 dcy

stealth address amount amount idx
00: cfb1c02c1a8ec3e5b66351a94a25351e8fa737b0b6a5feb43aa19f02734070cd 0.613341830000 1362389 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": 905510, "vin": [ { "gen": { "height": 905500 } } ], "vout": [ { "amount": 613341830, "target": { "key": "cfb1c02c1a8ec3e5b66351a94a25351e8fa737b0b6a5feb43aa19f02734070cd" } } ], "extra": [ 1, 176, 233, 97, 25, 66, 90, 134, 8, 10, 81, 211, 241, 37, 93, 145, 221, 204, 119, 124, 161, 248, 58, 41, 48, 16, 193, 238, 85, 151, 146, 54, 203, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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