Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07fc234df32f254b65bc0d49d97f8d5f552a22c0325332da6a17be6715164dcd

Tx prefix hash: 0d77f15dcfad71ac03ebb9c996d535fac3c3664081a1cf8a07ea2ef23bfc2a2b
Tx public key: be2b19e172b0d9839451d5d02c51537ac8188005c013a161c507d621d31f7469
Timestamp: 1637826043 Timestamp [UCT]: 2021-11-25 07:40:43 Age [y:d:h:m:s]: 03:345:06:03:01
Block: 381670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1023152 RingCT/type: yes/0
Extra: 01be2b19e172b0d9839451d5d02c51537ac8188005c013a161c507d621d31f7469021100000003e9564d6f000000000000000000

1 output(s) for total of 33.371000657000 dcy

stealth address amount amount idx
00: 0e1fb31e943e5c6d7fc005ce53865d26a316d37ea728ee2302a9165d061f8cee 33.371000657000 770998 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": 381680, "vin": [ { "gen": { "height": 381670 } } ], "vout": [ { "amount": 33371000657, "target": { "key": "0e1fb31e943e5c6d7fc005ce53865d26a316d37ea728ee2302a9165d061f8cee" } } ], "extra": [ 1, 190, 43, 25, 225, 114, 176, 217, 131, 148, 81, 213, 208, 44, 81, 83, 122, 200, 24, 128, 5, 192, 19, 161, 97, 197, 7, 214, 33, 211, 31, 116, 105, 2, 17, 0, 0, 0, 3, 233, 86, 77, 111, 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