Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2304cb2282bcbeea9abd72b4044cf11c1b8f389f3ee4061ba7b5c59c83ac70b7

Tx prefix hash: baeec5f0597363693da9a4c51f181dad73500c22dfb5c304bc5ca63e9cd59aab
Tx public key: d3ab5a7f6debf461c981f2134f1f2c6f26be414843859d5f44d89fccf303cd2e
Timestamp: 1702734004 Timestamp [UCT]: 2023-12-16 13:40:04 Age [y:d:h:m:s]: 01:035:22:19:17
Block: 914402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287000 RingCT/type: yes/0
Extra: 01d3ab5a7f6debf461c981f2134f1f2c6f26be414843859d5f44d89fccf303cd2e02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 588f6d3f6b8c07254450ed124063b9f24dcc52017d0077871986e29ac3e8325a 0.600000000000 1371716 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": 914412, "vin": [ { "gen": { "height": 914402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "588f6d3f6b8c07254450ed124063b9f24dcc52017d0077871986e29ac3e8325a" } } ], "extra": [ 1, 211, 171, 90, 127, 109, 235, 244, 97, 201, 129, 242, 19, 79, 31, 44, 111, 38, 190, 65, 72, 67, 133, 157, 95, 68, 216, 159, 204, 243, 3, 205, 46, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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