Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85b7c09552e027048fb93ccbad4bb6de133376924d97fa703faccc631f8c017d

Tx prefix hash: f05c6036418bc21081a316933b830e454c585145a684f21f20a1777e49a0fdc7
Tx public key: 94e61cd553bf8053decb5dba55d64ed06468d6c5b9d930e2cc74554ebcebeb7c
Timestamp: 1576513138 Timestamp [UCT]: 2019-12-16 16:18:58 Age [y:d:h:m:s]: 05:079:04:34:19
Block: 27917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1203567 RingCT/type: yes/0
Extra: 0194e61cd553bf8053decb5dba55d64ed06468d6c5b9d930e2cc74554ebcebeb7c02110000000d8a2ee0d9000000000000000000

1 output(s) for total of 496.021219140000 dcy

stealth address amount amount idx
00: 9a308c16ac28dcb58da30ff494deed1e5cf488f2c60e2782dc5a8568f143f75d 496.021219140000 46181 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": 27927, "vin": [ { "gen": { "height": 27917 } } ], "vout": [ { "amount": 496021219140, "target": { "key": "9a308c16ac28dcb58da30ff494deed1e5cf488f2c60e2782dc5a8568f143f75d" } } ], "extra": [ 1, 148, 230, 28, 213, 83, 191, 128, 83, 222, 203, 93, 186, 85, 214, 78, 208, 100, 104, 214, 197, 185, 217, 48, 226, 204, 116, 85, 78, 188, 235, 235, 124, 2, 17, 0, 0, 0, 13, 138, 46, 224, 217, 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