Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f4dc7e43eac7329fefcdf382116fff787840dc7e8f514cf8c98b9c1f6f4340c

Tx prefix hash: 5017f634a9b7d7b740b0e413fd6f4aeee54bc3ff238235e9cba4b2ca0c3db93e
Tx public key: 0e88cabf7f5cdaf494e4448710a7e95ea77cbb7e752b14ce4ad9dce9f209ceb6
Timestamp: 1765791266 Timestamp [UCT]: 2025-12-15 09:34:26 Age [y:d:h:m:s]: 00:008:10:40:50
Block: 1434047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6048 RingCT/type: yes/0
Extra: 010e88cabf7f5cdaf494e4448710a7e95ea77cbb7e752b14ce4ad9dce9f209ceb60211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06fc26d93be83182ec8387bdbb8bfbc8d33ccc5ad627a249e8f16b8607c0573e 0.600000000000 1922828 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": 1434057, "vin": [ { "gen": { "height": 1434047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06fc26d93be83182ec8387bdbb8bfbc8d33ccc5ad627a249e8f16b8607c0573e" } } ], "extra": [ 1, 14, 136, 202, 191, 127, 92, 218, 244, 148, 228, 68, 135, 16, 167, 233, 94, 167, 124, 187, 126, 117, 43, 20, 206, 74, 217, 220, 233, 242, 9, 206, 182, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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