Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e561c174c9bd7fb1963d9581439350e3db34e3cc77a6bebaf2b7804cfe59f681

Tx prefix hash: 2d5d38e6df169b049c1249d167ea10d43508876e8a552c82fbee908f44939fd8
Tx public key: 469ba09b3b9a3d3739aea70521e993c95d371b66cc48235e8b4eeeb895dcef7f
Timestamp: 1681036260 Timestamp [UCT]: 2023-04-09 10:31:00 Age [y:d:h:m:s]: 01:276:11:05:30
Block: 734786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459083 RingCT/type: yes/0
Extra: 01469ba09b3b9a3d3739aea70521e993c95d371b66cc48235e8b4eeeb895dcef7f021100000006faf35c9c000000000000000000

1 output(s) for total of 2.256052404000 dcy

stealth address amount amount idx
00: 150f8bcbc54bde0d196ecc675bc0f1058e6d351127a2e2964b094250044d3759 2.256052404000 1181039 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": 734796, "vin": [ { "gen": { "height": 734786 } } ], "vout": [ { "amount": 2256052404, "target": { "key": "150f8bcbc54bde0d196ecc675bc0f1058e6d351127a2e2964b094250044d3759" } } ], "extra": [ 1, 70, 155, 160, 155, 59, 154, 61, 55, 57, 174, 167, 5, 33, 233, 147, 201, 93, 55, 27, 102, 204, 72, 35, 94, 139, 78, 238, 184, 149, 220, 239, 127, 2, 17, 0, 0, 0, 6, 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