Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 023abf6c34c99a15164bf32455d23dc3d49dc0358fb9bfd43cfabe3a55c0e3a1

Tx prefix hash: 4540d2e373afb45d5df2225add316b36a4cba16d5fbf17bf9589449c9befb525
Tx public key: b503d8a792e72d6e1e9d0d3f7370df4fbb2f571b3a1f12e49e163059602d31e2
Timestamp: 1737233641 Timestamp [UCT]: 2025-01-18 20:54:01 Age [y:d:h:m:s]: 00:151:06:59:32
Block: 1200251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107835 RingCT/type: yes/0
Extra: 01b503d8a792e72d6e1e9d0d3f7370df4fbb2f571b3a1f12e49e163059602d31e2021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd5dd86ec2640ea98fc8061457be74997f6e19f23769945a5a29100e11a31807 0.600000000000 1686894 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": 1200261, "vin": [ { "gen": { "height": 1200251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd5dd86ec2640ea98fc8061457be74997f6e19f23769945a5a29100e11a31807" } } ], "extra": [ 1, 181, 3, 216, 167, 146, 231, 45, 110, 30, 157, 13, 63, 115, 112, 223, 79, 187, 47, 87, 27, 58, 31, 18, 228, 158, 22, 48, 89, 96, 45, 49, 226, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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