Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bc9837158fe6b7450cfed6310b8d12d76a94691dbff2d742dafe010d08f1e25

Tx prefix hash: aa773bbf2290d0367dfe9b46dc208f0f5f92dc8b96f994de06b30177f20f8e88
Tx public key: 9e5be9df52b20f5bcdac137c943eeac794da7b464da755a588c1733c0a7090fd
Timestamp: 1761560431 Timestamp [UCT]: 2025-10-27 10:20:31 Age [y:d:h:m:s]: 00:010:11:55:03
Block: 1399006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7498 RingCT/type: yes/0
Extra: 019e5be9df52b20f5bcdac137c943eeac794da7b464da755a588c1733c0a7090fd021100000005df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 500a6a99704c32e3c8767acd2e58f0fd935714f4b38283351b214ead4f732ac0 0.600000000000 1887309 of 15

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": 1399016, "vin": [ { "gen": { "height": 1399006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "500a6a99704c32e3c8767acd2e58f0fd935714f4b38283351b214ead4f732ac0" } } ], "extra": [ 1, 158, 91, 233, 223, 82, 178, 15, 91, 205, 172, 19, 124, 148, 62, 234, 199, 148, 218, 123, 70, 77, 167, 85, 165, 136, 193, 115, 60, 10, 112, 144, 253, 2, 17, 0, 0, 0, 5, 223, 90, 36, 122, 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