Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14fcc44e96556c8f689255306e45ad21971d617a5e7bf6ff5af0ae70901a4edb

Tx prefix hash: 031f3275d154e502b8acb755eb9f2a3a70e2c98ec96f946c8b4eac5b765aafaa
Tx public key: d731f19dfc6a0587f8028f9a86905e58b6560cfa4a297eecb938522352cd41ca
Timestamp: 1725599504 Timestamp [UCT]: 2024-09-06 05:11:44 Age [y:d:h:m:s]: 00:169:15:10:57
Block: 1103985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121028 RingCT/type: yes/0
Extra: 01d731f19dfc6a0587f8028f9a86905e58b6560cfa4a297eecb938522352cd41ca021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02a203b3e09ef8449c33e01657d4662ee0de41e479323cbc1f692bba32674ae8 0.600000000000 1581026 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": 1103995, "vin": [ { "gen": { "height": 1103985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02a203b3e09ef8449c33e01657d4662ee0de41e479323cbc1f692bba32674ae8" } } ], "extra": [ 1, 215, 49, 241, 157, 252, 106, 5, 135, 248, 2, 143, 154, 134, 144, 94, 88, 182, 86, 12, 250, 74, 41, 126, 236, 185, 56, 82, 35, 82, 205, 65, 202, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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