Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c18755692c9e4f4d07c9f3c9c674a69499241c81d51006f4f905e44aa8dfe940

Tx prefix hash: 205d99c1496b5b4b862cf1f65b6e4f7bde8d391c743e63ef43f00835e1b98201
Tx public key: 641a3118b81dbf924bbbb0f8ca5dcee0079c892620355f56bf922edd5a1de8e2
Timestamp: 1607884463 Timestamp [UCT]: 2020-12-13 18:34:23 Age [y:d:h:m:s]: 04:054:19:32:58
Block: 161386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1051301 RingCT/type: yes/0
Extra: 01641a3118b81dbf924bbbb0f8ca5dcee0079c892620355f56bf922edd5a1de8e2021100000b724ea414e5000000000000000000

1 output(s) for total of 179.168585853000 dcy

stealth address amount amount idx
00: 4f14ca1502680eb24c7e5f068d0c9fcf7cf8eff4922393dabb9be4bf0b6e8aa0 179.168585853000 286007 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": 161396, "vin": [ { "gen": { "height": 161386 } } ], "vout": [ { "amount": 179168585853, "target": { "key": "4f14ca1502680eb24c7e5f068d0c9fcf7cf8eff4922393dabb9be4bf0b6e8aa0" } } ], "extra": [ 1, 100, 26, 49, 24, 184, 29, 191, 146, 75, 187, 176, 248, 202, 93, 206, 224, 7, 156, 137, 38, 32, 53, 95, 86, 191, 146, 46, 221, 90, 29, 232, 226, 2, 17, 0, 0, 11, 114, 78, 164, 20, 229, 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