Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e831178dbc02050ca293dd0b052c2f6f5a0426a5f152cede2b1661f14987e2b

Tx prefix hash: 67240ad8d5dd1b26d8790b76f84bc8fb8393bad288e9cf33e0450ac7150692bf
Tx public key: f4a99dd9960fb79e038a2a31fc85dac75b6669f9e09e726a372b3ba93b5d6444
Timestamp: 1747495279 Timestamp [UCT]: 2025-05-17 15:21:19 Age [y:d:h:m:s]: 00:187:23:43:24
Block: 1284963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132057 RingCT/type: yes/0
Extra: 01f4a99dd9960fb79e038a2a31fc85dac75b6669f9e09e726a372b3ba93b5d64440211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc5a195483ac6fddf2e899e45cdc4fdbe7f036728e843f4de748bd58503fb953 0.600000000000 1772426 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": 1284973, "vin": [ { "gen": { "height": 1284963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc5a195483ac6fddf2e899e45cdc4fdbe7f036728e843f4de748bd58503fb953" } } ], "extra": [ 1, 244, 169, 157, 217, 150, 15, 183, 158, 3, 138, 42, 49, 252, 133, 218, 199, 91, 102, 105, 249, 224, 158, 114, 106, 55, 43, 59, 169, 59, 93, 100, 68, 2, 17, 0, 0, 0, 1, 31, 144, 81, 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