Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfe7de7a16e6da3da6e8efe09a66b33dff416c90ede1516d7e1ee9c3254c36c0

Tx prefix hash: de6624401529beac13535f4f081a8d0a400e8792b231a1121cc11ac99cddf4a3
Tx public key: 77adc49c4605a4322197f8cdaaa3d2761f3ed07dc06d61e9b29960da4676baaf
Timestamp: 1582960511 Timestamp [UCT]: 2020-02-29 07:15:11 Age [y:d:h:m:s]: 04:299:00:30:15
Block: 73810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107517 RingCT/type: yes/0
Extra: 0177adc49c4605a4322197f8cdaaa3d2761f3ed07dc06d61e9b29960da4676baaf02110000001f724f989b000000000000000000

1 output(s) for total of 349.492313840000 dcy

stealth address amount amount idx
00: 41383a7ef2cb780f12404d1313d4bb49cdbfa965751774ee4f6ecc222e52b126 349.492313840000 136331 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": 73820, "vin": [ { "gen": { "height": 73810 } } ], "vout": [ { "amount": 349492313840, "target": { "key": "41383a7ef2cb780f12404d1313d4bb49cdbfa965751774ee4f6ecc222e52b126" } } ], "extra": [ 1, 119, 173, 196, 156, 70, 5, 164, 50, 33, 151, 248, 205, 170, 163, 210, 118, 31, 62, 208, 125, 192, 109, 97, 233, 178, 153, 96, 218, 70, 118, 186, 175, 2, 17, 0, 0, 0, 31, 114, 79, 152, 155, 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