Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bd71a19d1f7b25ac5144bf38ec6970572e751b04c89d88b3cf591d2f796b9f1

Tx prefix hash: 3129959e0d61623ffef873873b0b66fbe801ce10424dc8755beb114f2c6a1651
Tx public key: 7150e5ddb137499d9388348e68d419101107fdd0a0b30b5c498c3d1e3fa55727
Timestamp: 1712237982 Timestamp [UCT]: 2024-04-04 13:39:42 Age [y:d:h:m:s]: 00:220:20:16:05
Block: 993172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158122 RingCT/type: yes/0
Extra: 017150e5ddb137499d9388348e68d419101107fdd0a0b30b5c498c3d1e3fa5572702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d0cc760b12d89f445ff0bd8b5076c63985ae2fd798f38b11950f75f98f9d281 0.600000000000 1453554 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": 993182, "vin": [ { "gen": { "height": 993172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d0cc760b12d89f445ff0bd8b5076c63985ae2fd798f38b11950f75f98f9d281" } } ], "extra": [ 1, 113, 80, 229, 221, 177, 55, 73, 157, 147, 136, 52, 142, 104, 212, 25, 16, 17, 7, 253, 208, 160, 179, 11, 92, 73, 140, 61, 30, 63, 165, 87, 39, 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