Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51f1a43826ef76d839579f03789813dd75b0e3f77f75fa25b0d93c24dc7c8fab

Tx prefix hash: 35000085c0ab15dbbac71b8f9e3f604f32ec369cdb8bf39c701449073b41f2b7
Tx public key: d0c159b327fcc73b43cf7f030ce0e407ebe5517693f5304273e764f8ad4f7656
Timestamp: 1610036864 Timestamp [UCT]: 2021-01-07 16:27:44 Age [y:d:h:m:s]: 03:316:11:14:59
Block: 175887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 980966 RingCT/type: yes/0
Extra: 01d0c159b327fcc73b43cf7f030ce0e407ebe5517693f5304273e764f8ad4f765602110000026390ce5c0f000000000000000000

1 output(s) for total of 160.403563397000 dcy

stealth address amount amount idx
00: c224131dc5b7767fc0d5bce70d00bae526e1815e5a35cf0090f2b8480ef94ec1 160.403563397000 336391 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": 175897, "vin": [ { "gen": { "height": 175887 } } ], "vout": [ { "amount": 160403563397, "target": { "key": "c224131dc5b7767fc0d5bce70d00bae526e1815e5a35cf0090f2b8480ef94ec1" } } ], "extra": [ 1, 208, 193, 89, 179, 39, 252, 199, 59, 67, 207, 127, 3, 12, 224, 228, 7, 235, 229, 81, 118, 147, 245, 48, 66, 115, 231, 100, 248, 173, 79, 118, 86, 2, 17, 0, 0, 2, 99, 144, 206, 92, 15, 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