Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f46ab679dbca931ecb9618637f05a352bee7ecee0d00b434c4109713fca63c39

Tx prefix hash: 5f686369c8d21a48c973d433544fa79c98f0cd2a5c00ed327e8acee9cf5e4599
Tx public key: b9ef9c4e840f1f18ecd93ffc47af24d60542ceaeee1b32223ff8d763d15f6540
Timestamp: 1760829902 Timestamp [UCT]: 2025-10-18 23:25:02 Age [y:d:h:m:s]: 00:081:09:29:27
Block: 1392953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58271 RingCT/type: yes/0
Extra: 01b9ef9c4e840f1f18ecd93ffc47af24d60542ceaeee1b32223ff8d763d15f65400211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a0db1fe5a69908ae1997f5eace5a55ec550f0a35430e339bf88e5c4cd0f13ba 0.600000000000 1881210 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": 1392963, "vin": [ { "gen": { "height": 1392953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a0db1fe5a69908ae1997f5eace5a55ec550f0a35430e339bf88e5c4cd0f13ba" } } ], "extra": [ 1, 185, 239, 156, 78, 132, 15, 31, 24, 236, 217, 63, 252, 71, 175, 36, 214, 5, 66, 206, 174, 238, 27, 50, 34, 63, 248, 215, 99, 209, 95, 101, 64, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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