Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b75b515b622eba267efc3bbc6ef2927b59fc682a1cb2e05239b431f03384a23

Tx prefix hash: f1d9855f2ab6c211ec03a59ea0d7f1e70991015b81e37333fbb3117b42649d40
Tx public key: 4712779254593fc8ae2327c85a8b6cb2e8e34406e41ac2f3fbada73b86e67d33
Timestamp: 1736026101 Timestamp [UCT]: 2025-01-04 21:28:21 Age [y:d:h:m:s]: 00:071:15:02:33
Block: 1190289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50980 RingCT/type: yes/0
Extra: 014712779254593fc8ae2327c85a8b6cb2e8e34406e41ac2f3fbada73b86e67d33021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76320531e0778a1feb882eeb1166d527a11cfcb09534f602cb7857819a989c4b 0.600000000000 1676804 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": 1190299, "vin": [ { "gen": { "height": 1190289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76320531e0778a1feb882eeb1166d527a11cfcb09534f602cb7857819a989c4b" } } ], "extra": [ 1, 71, 18, 119, 146, 84, 89, 63, 200, 174, 35, 39, 200, 90, 139, 108, 178, 232, 227, 68, 6, 228, 26, 194, 243, 251, 173, 167, 59, 134, 230, 125, 51, 2, 17, 0, 0, 0, 5, 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