Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f544c89c2daf6e2d5d03fed8b1b9e3785c40a4d19a4c4fc44be7d18ea4e87f2

Tx prefix hash: 495cc23856386366e2835af3d4a54e1577348cd736cacaa433054182ab46ae3c
Tx public key: 19dd9ee6090c921ae3838a5b42653aa66964a5e40a51e3408994ab00e9102ad3
Timestamp: 1724676564 Timestamp [UCT]: 2024-08-26 12:49:24 Age [y:d:h:m:s]: 00:136:05:56:27
Block: 1096318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97459 RingCT/type: yes/0
Extra: 0119dd9ee6090c921ae3838a5b42653aa66964a5e40a51e3408994ab00e9102ad3021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e702b4cfa5767a61e60f459a6d523d52991cb71d023fd2255152857f4688f2c3 0.600000000000 1571507 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": 1096328, "vin": [ { "gen": { "height": 1096318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e702b4cfa5767a61e60f459a6d523d52991cb71d023fd2255152857f4688f2c3" } } ], "extra": [ 1, 25, 221, 158, 230, 9, 12, 146, 26, 227, 131, 138, 91, 66, 101, 58, 166, 105, 100, 165, 228, 10, 81, 227, 64, 137, 148, 171, 0, 233, 16, 42, 211, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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