Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 675263363f56f953f018e17ee672d50134ab270814c30f41e891c8a2bbaa5fcf

Tx prefix hash: ec2b680f55a849023abeaf83aaca4d19659d0f3714735325cca82d3934b6c7ea
Tx public key: 0bf3ff5f5d8ab176076e2c2ab8f92ec5b7d9c4cb6add57e4cca2b3e02aeca472
Timestamp: 1719800338 Timestamp [UCT]: 2024-07-01 02:18:58 Age [y:d:h:m:s]: 00:256:22:34:41
Block: 1055896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183599 RingCT/type: yes/0
Extra: 010bf3ff5f5d8ab176076e2c2ab8f92ec5b7d9c4cb6add57e4cca2b3e02aeca4720211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba235356ea31a99d567f60e825568ffcb50880b239c51d995ee8c642403ab0fb 0.600000000000 1526303 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": 1055906, "vin": [ { "gen": { "height": 1055896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba235356ea31a99d567f60e825568ffcb50880b239c51d995ee8c642403ab0fb" } } ], "extra": [ 1, 11, 243, 255, 95, 93, 138, 177, 118, 7, 110, 44, 42, 184, 249, 46, 197, 183, 217, 196, 203, 106, 221, 87, 228, 204, 162, 179, 224, 42, 236, 164, 114, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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