Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77250bda5bc212c8113e71e08cd37698cc8796a69198ae495170162519e08d7f

Tx prefix hash: bf84b91946cc276f9e446826249a16dd225b3102b3a8ee762aac16fb1da9c38a
Tx public key: 43b5cf98c0cc84b6976414bebe07d0cf831cddc7ff9f321248d98644e1f5b44d
Timestamp: 1695492295 Timestamp [UCT]: 2023-09-23 18:04:55 Age [y:d:h:m:s]: 01:224:01:43:49
Block: 854567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421231 RingCT/type: yes/0
Extra: 0143b5cf98c0cc84b6976414bebe07d0cf831cddc7ff9f321248d98644e1f5b44d02110000000b4b8f5122000000000000000000

1 output(s) for total of 0.904617180000 dcy

stealth address amount amount idx
00: 38c9fdd79b322b384c77864b81b7e783efbe758f61153bfe288d2342e8656e4a 0.904617180000 1308549 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": 854577, "vin": [ { "gen": { "height": 854567 } } ], "vout": [ { "amount": 904617180, "target": { "key": "38c9fdd79b322b384c77864b81b7e783efbe758f61153bfe288d2342e8656e4a" } } ], "extra": [ 1, 67, 181, 207, 152, 192, 204, 132, 182, 151, 100, 20, 190, 190, 7, 208, 207, 131, 28, 221, 199, 255, 159, 50, 18, 72, 217, 134, 68, 225, 245, 180, 77, 2, 17, 0, 0, 0, 11, 75, 143, 81, 34, 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