Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 273afc487e890da61ff87bd9272b7d1ced959f10e3246f4e807076ccd05f01d8

Tx prefix hash: 37422c721c99227a2824229cb6893201d5c49584efb0d0deef1bf2d311171ffe
Tx public key: d784e1afcc4cf738ae332f2c2ceb24dd30f6acf1d620122f66165a31910afe92
Timestamp: 1663879094 Timestamp [UCT]: 2022-09-22 20:38:14 Age [y:d:h:m:s]: 03:039:06:28:33
Block: 593605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 808048 RingCT/type: yes/0
Extra: 01d784e1afcc4cf738ae332f2c2ceb24dd30f6acf1d620122f66165a31910afe92021100000001faf35c9c000000000000000000

1 output(s) for total of 6.624304493000 dcy

stealth address amount amount idx
00: 940138ec52c5d897a56dc0804c15f60b1bf490c8108e5a4dea27399e4958e25f 6.624304493000 1028404 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": 593615, "vin": [ { "gen": { "height": 593605 } } ], "vout": [ { "amount": 6624304493, "target": { "key": "940138ec52c5d897a56dc0804c15f60b1bf490c8108e5a4dea27399e4958e25f" } } ], "extra": [ 1, 215, 132, 225, 175, 204, 76, 247, 56, 174, 51, 47, 44, 44, 235, 36, 221, 48, 246, 172, 241, 214, 32, 18, 47, 102, 22, 90, 49, 145, 10, 254, 146, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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