Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5197e11d055858c58d67106f1f503b22c278926c1470b119c7637c21dd51ad6

Tx prefix hash: baed906bde8149d8b03c2a84d2e13e86c74aa43325042aa0e2b3cf383c5a9447
Tx public key: 3cd22f9ef133e054ea25fe4be441fd0bcf30d5f2556beb353a474a2e2a844748
Timestamp: 1685073928 Timestamp [UCT]: 2023-05-26 04:05:28 Age [y:d:h:m:s]: 02:159:02:18:00
Block: 768250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 633498 RingCT/type: yes/0
Extra: 013cd22f9ef133e054ea25fe4be441fd0bcf30d5f2556beb353a474a2e2a84474802110000000433af99f4000000000000000000

1 output(s) for total of 1.747708549000 dcy

stealth address amount amount idx
00: 55040893212fbbd19f2ed31f4ed0a6c95e48ab42f9e85d753937c44dbc92f283 1.747708549000 1217441 of 0

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": 768260, "vin": [ { "gen": { "height": 768250 } } ], "vout": [ { "amount": 1747708549, "target": { "key": "55040893212fbbd19f2ed31f4ed0a6c95e48ab42f9e85d753937c44dbc92f283" } } ], "extra": [ 1, 60, 210, 47, 158, 241, 51, 224, 84, 234, 37, 254, 75, 228, 65, 253, 11, 207, 48, 213, 242, 85, 107, 235, 53, 58, 71, 74, 46, 42, 132, 71, 72, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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