Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 531c3452ecfa977739f08d3666b33ea81aa22ec3aa24570d1dabc1a24f62a581

Tx prefix hash: 48e7eb72a3fdb57bdbd274e2cbdc53f023c53c67f8d19ece8752c07193c75b5e
Tx public key: 552fc2ab0fd36eda930420f73d8007a805046c1e55fe2b1eb72b647436461ea5
Timestamp: 1734219374 Timestamp [UCT]: 2024-12-14 23:36:14 Age [y:d:h:m:s]: 00:109:19:06:44
Block: 1175351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78233 RingCT/type: yes/0
Extra: 01552fc2ab0fd36eda930420f73d8007a805046c1e55fe2b1eb72b647436461ea5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 588d1487a7b0291d46a9935b737e7c7a2b3a3810a56afae7d5a17c974310f528 0.600000000000 1661620 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": 1175361, "vin": [ { "gen": { "height": 1175351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "588d1487a7b0291d46a9935b737e7c7a2b3a3810a56afae7d5a17c974310f528" } } ], "extra": [ 1, 85, 47, 194, 171, 15, 211, 110, 218, 147, 4, 32, 247, 61, 128, 7, 168, 5, 4, 108, 30, 85, 254, 43, 30, 183, 43, 100, 116, 54, 70, 30, 165, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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