Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bce751866cc259775a47740b9f944b3c0be8cc8e10f77a2b1e9e5101f47567d

Tx prefix hash: dfcbfb691e1cd1ffd60414d64307071dabb1fd9f9d0208b8535e46cdf1717509
Tx public key: 471df201b40f23e12d59d4b47f70fb9dd18049e20122a1d0af019050efeb59ce
Timestamp: 1727787781 Timestamp [UCT]: 2024-10-01 13:03:01 Age [y:d:h:m:s]: 01:040:23:58:00
Block: 1122123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287689 RingCT/type: yes/0
Extra: 01471df201b40f23e12d59d4b47f70fb9dd18049e20122a1d0af019050efeb59ce02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d7e573cba897a57cb6060d451fe7d8ecbc8ca25b36309f54096fc404a1da2e6 0.600000000000 1604506 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": 1122133, "vin": [ { "gen": { "height": 1122123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d7e573cba897a57cb6060d451fe7d8ecbc8ca25b36309f54096fc404a1da2e6" } } ], "extra": [ 1, 71, 29, 242, 1, 180, 15, 35, 225, 45, 89, 212, 180, 127, 112, 251, 157, 209, 128, 73, 226, 1, 34, 161, 208, 175, 1, 144, 80, 239, 235, 89, 206, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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