Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 208da17507dec39d8742eaa4bf97d0f976252cd2e365bbefb704b917e1b4515d

Tx prefix hash: fcabe5868ef0b3bb5c15899bc70baf84969406ce0b0a7b646804aa36e63b8cb3
Tx public key: eaf3507bb0cd6f51992a940d2d9095b330bda508ce5a1c1ff0f164afe44c30a2
Timestamp: 1720834382 Timestamp [UCT]: 2024-07-13 01:33:02 Age [y:d:h:m:s]: 00:245:13:19:52
Block: 1064487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175428 RingCT/type: yes/0
Extra: 01eaf3507bb0cd6f51992a940d2d9095b330bda508ce5a1c1ff0f164afe44c30a202110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c57607afca851f6da2c09b5fb293eb91e56c6db6ec0f20bd206430ddf5abed5e 0.600000000000 1535014 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": 1064497, "vin": [ { "gen": { "height": 1064487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c57607afca851f6da2c09b5fb293eb91e56c6db6ec0f20bd206430ddf5abed5e" } } ], "extra": [ 1, 234, 243, 80, 123, 176, 205, 111, 81, 153, 42, 148, 13, 45, 144, 149, 179, 48, 189, 165, 8, 206, 90, 28, 31, 240, 241, 100, 175, 228, 76, 48, 162, 2, 17, 0, 0, 0, 11, 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