Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af19790557e5e0d9d8cafdb7d7716f8d01df0ef6a6cfb74473a58c7694898f16

Tx prefix hash: e142743d02d0ce3d0dd31440be63e74be313f16fd8d1af0b567be6693c30c679
Tx public key: 51d7952640eecfa0e2f1507a11ea37c25f2c7e479462923b9fabc61e6d4d6ddb
Timestamp: 1581091838 Timestamp [UCT]: 2020-02-07 16:10:38 Age [y:d:h:m:s]: 04:282:16:07:56
Block: 60731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093388 RingCT/type: yes/0
Extra: 0151d7952640eecfa0e2f1507a11ea37c25f2c7e479462923b9fabc61e6d4d6ddb0211000000040aca7173000000000000000000

1 output(s) for total of 386.165795462000 dcy

stealth address amount amount idx
00: 1873717ef21543426bf38ae34ad74d0fa1737a792da9043f595322091801e101 386.165795462000 111798 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": 60741, "vin": [ { "gen": { "height": 60731 } } ], "vout": [ { "amount": 386165795462, "target": { "key": "1873717ef21543426bf38ae34ad74d0fa1737a792da9043f595322091801e101" } } ], "extra": [ 1, 81, 215, 149, 38, 64, 238, 207, 160, 226, 241, 80, 122, 17, 234, 55, 194, 95, 44, 126, 71, 148, 98, 146, 59, 159, 171, 198, 30, 109, 77, 109, 219, 2, 17, 0, 0, 0, 4, 10, 202, 113, 115, 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