Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05707bfd7ebd1f5d1f7183152a6d14a93a33a086cec32e2313cc566aa5998239

Tx prefix hash: 477b65ecce960613b369335145166f59f112b8f016764f2d7188c23d2f2a826b
Tx public key: 61bc94c353ec32db6910f4dedae2c6ede7a3b5f2335245f6b7a289773fa1866f
Timestamp: 1696837725 Timestamp [UCT]: 2023-10-09 07:48:45 Age [y:d:h:m:s]: 02:030:11:21:54
Block: 865739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541393 RingCT/type: yes/0
Extra: 0161bc94c353ec32db6910f4dedae2c6ede7a3b5f2335245f6b7a289773fa1866f02110000000233af99f4000000000000000000

1 output(s) for total of 0.830705988000 dcy

stealth address amount amount idx
00: d07614bca3c808ea98bd267d36fb0cd802adf08efe6f07ea83087572514a5047 0.830705988000 1320285 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": 865749, "vin": [ { "gen": { "height": 865739 } } ], "vout": [ { "amount": 830705988, "target": { "key": "d07614bca3c808ea98bd267d36fb0cd802adf08efe6f07ea83087572514a5047" } } ], "extra": [ 1, 97, 188, 148, 195, 83, 236, 50, 219, 105, 16, 244, 222, 218, 226, 198, 237, 231, 163, 181, 242, 51, 82, 69, 246, 183, 162, 137, 119, 63, 161, 134, 111, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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