Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be53f8c2d16723c4f2492052dda5ae6d077bf76fdff45baaa07833e2b4c9d012

Tx prefix hash: 0f2858f52015872bf43c5c1f71101ae6b80545c020167eeed529a4a1b739cae4
Tx public key: 13225aa0df7038daac3688637a174c706e0142f9db519371a20ac3dd8e6eb24f
Timestamp: 1684880688 Timestamp [UCT]: 2023-05-23 22:24:48 Age [y:d:h:m:s]: 01:325:18:08:08
Block: 766645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494049 RingCT/type: yes/0
Extra: 0113225aa0df7038daac3688637a174c706e0142f9db519371a20ac3dd8e6eb24f02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.769241201000 dcy

stealth address amount amount idx
00: 261791203cfbd0b39f31bc3f7ff755eb424bc7169052541e28b4873ccb2c3be5 1.769241201000 1215700 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": 766655, "vin": [ { "gen": { "height": 766645 } } ], "vout": [ { "amount": 1769241201, "target": { "key": "261791203cfbd0b39f31bc3f7ff755eb424bc7169052541e28b4873ccb2c3be5" } } ], "extra": [ 1, 19, 34, 90, 160, 223, 112, 56, 218, 172, 54, 136, 99, 122, 23, 76, 112, 110, 1, 66, 249, 219, 81, 147, 113, 162, 10, 195, 221, 142, 110, 178, 79, 2, 17, 0, 0, 0, 3, 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