Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c90367cc1d9fd708c9902dd6ec8df668c71db2fb5f5435e9a952992adb3809d

Tx prefix hash: b19d873e071cf2af06a9a13098230632834e49f88d3feee35ced2dbfc2df6b30
Tx public key: a6149875ed30ca065bb6cf567deeafd1ce86d279a487e8df18ea4af3f3f0a78d
Timestamp: 1735873403 Timestamp [UCT]: 2025-01-03 03:03:23 Age [y:d:h:m:s]: 00:309:13:21:07
Block: 1189022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218744 RingCT/type: yes/0
Extra: 01a6149875ed30ca065bb6cf567deeafd1ce86d279a487e8df18ea4af3f3f0a78d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0baea9e71bc10e4435706469fac8e74d2aa5ad92ea87cd962c544250daf861b0 0.600000000000 1675527 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": 1189032, "vin": [ { "gen": { "height": 1189022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0baea9e71bc10e4435706469fac8e74d2aa5ad92ea87cd962c544250daf861b0" } } ], "extra": [ 1, 166, 20, 152, 117, 237, 48, 202, 6, 91, 182, 207, 86, 125, 238, 175, 209, 206, 134, 210, 121, 164, 135, 232, 223, 24, 234, 74, 243, 243, 240, 167, 141, 2, 17, 0, 0, 0, 4, 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