Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64f0580fad4d27a3f2f2b4382bf000a1940ef7f36729121ba981fee3786c6b7c

Tx prefix hash: ee445f9bd95be121414fe623a7f8898ce03a64c17ac311d319af3b48784826a4
Tx public key: e7b4a3986a799503d186a5afe8fb0157c62951ef5eea8721d94159f74aca7188
Timestamp: 1710783166 Timestamp [UCT]: 2024-03-18 17:32:46 Age [y:d:h:m:s]: 01:019:03:05:45
Block: 981166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274619 RingCT/type: yes/0
Extra: 01e7b4a3986a799503d186a5afe8fb0157c62951ef5eea8721d94159f74aca718802110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b1fd7356f086fb6f2e66952a56375315881f2719b67587e340c2c7dd32d925a 0.600000000000 1441259 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": 981176, "vin": [ { "gen": { "height": 981166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b1fd7356f086fb6f2e66952a56375315881f2719b67587e340c2c7dd32d925a" } } ], "extra": [ 1, 231, 180, 163, 152, 106, 121, 149, 3, 209, 134, 165, 175, 232, 251, 1, 87, 198, 41, 81, 239, 94, 234, 135, 33, 217, 65, 89, 247, 74, 202, 113, 136, 2, 17, 0, 0, 0, 12, 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