Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 018a4f68e5c59942d40f09dd14c03afd5302c3f01624af6c3f971d2960dc3b0b

Tx prefix hash: 4ca4c2f31279c137682c5ade701a1876b001707763ca547f1b6f575f560afcaf
Tx public key: 36b621940c3c7e6124bb43a2f35df250970cff32cb2aa82fefdeefe4974e24e5
Timestamp: 1716353936 Timestamp [UCT]: 2024-05-22 04:58:56 Age [y:d:h:m:s]: 01:177:23:37:36
Block: 1027337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385802 RingCT/type: yes/0
Extra: 0136b621940c3c7e6124bb43a2f35df250970cff32cb2aa82fefdeefe4974e24e502110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b516d4949c217a4f043d442bd423cbd947f35298f688405ae59032e598eaf8a 0.600000000000 1494898 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": 1027347, "vin": [ { "gen": { "height": 1027337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b516d4949c217a4f043d442bd423cbd947f35298f688405ae59032e598eaf8a" } } ], "extra": [ 1, 54, 182, 33, 148, 12, 60, 126, 97, 36, 187, 67, 162, 243, 93, 242, 80, 151, 12, 255, 50, 203, 42, 168, 47, 239, 222, 239, 228, 151, 78, 36, 229, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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