Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 857f00d05eaaa955df4e96079dcf04cc3192eac753e244ef1116396c3e63f666

Tx prefix hash: 5ad56b55d38772fded91f8f0b468a9cd3dcaa5e9bc3aa3237533dcbcc5ca3d72
Tx public key: b77b1de30fc50452eb46361c19375e63b73a9f4513b4aee134530a2f6d1b3bc9
Timestamp: 1742865950 Timestamp [UCT]: 2025-03-25 01:25:50 Age [y:d:h:m:s]: 00:290:22:35:27
Block: 1246639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205759 RingCT/type: yes/0
Extra: 01b77b1de30fc50452eb46361c19375e63b73a9f4513b4aee134530a2f6d1b3bc9021100000003c6740958000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f17fd3474d18a8e7b23f397ac626d1819553e724e635040fa7be28d6848f831f 0.600000000000 1733640 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": 1246649, "vin": [ { "gen": { "height": 1246639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f17fd3474d18a8e7b23f397ac626d1819553e724e635040fa7be28d6848f831f" } } ], "extra": [ 1, 183, 123, 29, 227, 15, 197, 4, 82, 235, 70, 54, 28, 25, 55, 94, 99, 183, 58, 159, 69, 19, 180, 174, 225, 52, 83, 10, 47, 109, 27, 59, 201, 2, 17, 0, 0, 0, 3, 198, 116, 9, 88, 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