Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddff1870ab9b94f5112e6a79fab7615a755a4e605693525978607d4e325b76dc

Tx prefix hash: a76e41314404a1b659b553c08ba2c244fe78cd0b75dd8881a37b0a3db772c18e
Tx public key: a31664b04ec3e6f31060bdf0f505e769cea697a6778fc52aaba4cfbdc8a7f050
Timestamp: 1648177228 Timestamp [UCT]: 2022-03-25 03:00:28 Age [y:d:h:m:s]: 02:319:08:11:24
Block: 465826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 747494 RingCT/type: yes/0
Extra: 01a31664b04ec3e6f31060bdf0f505e769cea697a6778fc52aaba4cfbdc8a7f05002110000000b4da16a3a000000000000000000

1 output(s) for total of 17.560033658000 dcy

stealth address amount amount idx
00: f3bdaa7deab54a7327333a0deb4b2f18d5c2f064f42e1afdfe2045b27338c079 17.560033658000 884013 of 0

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": 465836, "vin": [ { "gen": { "height": 465826 } } ], "vout": [ { "amount": 17560033658, "target": { "key": "f3bdaa7deab54a7327333a0deb4b2f18d5c2f064f42e1afdfe2045b27338c079" } } ], "extra": [ 1, 163, 22, 100, 176, 78, 195, 230, 243, 16, 96, 189, 240, 245, 5, 231, 105, 206, 166, 151, 166, 119, 143, 197, 42, 171, 164, 207, 189, 200, 167, 240, 80, 2, 17, 0, 0, 0, 11, 77, 161, 106, 58, 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