Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19b262230f0a3263e122ff02785922a5e70d6ab1712d23a9ec0734451368fcd3

Tx prefix hash: 00d85dc585fe940fa056fc43d8a496df08d1a1d58967d6f8c077b3426a57bb65
Tx public key: 1d3b41e56bfad43d3bef4e1836af038d38f92ffc3e66d0207b9fa8f8b33c2a7d
Timestamp: 1746986446 Timestamp [UCT]: 2025-05-11 18:00:46 Age [y:d:h:m:s]: 00:193:20:40:37
Block: 1280759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136254 RingCT/type: yes/0
Extra: 011d3b41e56bfad43d3bef4e1836af038d38f92ffc3e66d0207b9fa8f8b33c2a7d0211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96aac95a7e87ff4a525b915d241b4d9dd45c7a66a96d371792c0a925c8f6fcef 0.600000000000 1768150 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": 1280769, "vin": [ { "gen": { "height": 1280759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96aac95a7e87ff4a525b915d241b4d9dd45c7a66a96d371792c0a925c8f6fcef" } } ], "extra": [ 1, 29, 59, 65, 229, 107, 250, 212, 61, 59, 239, 78, 24, 54, 175, 3, 141, 56, 249, 47, 252, 62, 102, 208, 32, 123, 159, 168, 248, 179, 60, 42, 125, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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