Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5058b4c291fb049c20d8492e3cd433f3f4dcb9ffe9a74b3410ad558e86056488

Tx prefix hash: c2a710af553c3466d01af01b5bb8c1dc9f6c06ed8a0739ed79bba1a9d0a49c49
Tx public key: 06732e9cbe1253803a9aa6e06e7c131142b471b98788fe6bf1f77304c15eecc4
Timestamp: 1703252837 Timestamp [UCT]: 2023-12-22 13:47:17 Age [y:d:h:m:s]: 01:145:14:23:39
Block: 918714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365198 RingCT/type: yes/0
Extra: 0106732e9cbe1253803a9aa6e06e7c131142b471b98788fe6bf1f77304c15eecc402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5c16f5003ac4c2d254c65b25a6d73d88de590536fc3015ccb47fa785071b7d1 0.600000000000 1376372 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": 918724, "vin": [ { "gen": { "height": 918714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5c16f5003ac4c2d254c65b25a6d73d88de590536fc3015ccb47fa785071b7d1" } } ], "extra": [ 1, 6, 115, 46, 156, 190, 18, 83, 128, 58, 154, 166, 224, 110, 124, 19, 17, 66, 180, 113, 185, 135, 136, 254, 107, 241, 247, 115, 4, 193, 94, 236, 196, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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